![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
create-pure
Advanced tools
Template to generate low maintenence JS modules
An opinionated template to optimize workflow for stressed out minimalists.
The template is intended for modules whose main purpose is to export functionality and published to a public registry.
(Don't use this for your main project, you'll most likely regret it)
Features
npm init telamon/pure my-awesome-module
That's it.
$ tree my-awesome-module
my-awesome-module/
├── .editorconfig
├── .gitignore
├── LICENSE
├── README.md
├── index.js
├── package.json
└── test.js
I lied, here is some "configuration"
REPO_PREFIX
git config --global npm.repoPrefix "https://github.com/telamon"
AUTHOR
git config --global user.name "First Last"
git config --global user.email "username@provider.tld"
DONATION_TEXT
git config --global npm.donation ~/Documents/advertisment.md
This section contains the contents for all files that this template generates. The generation code is located in index.js
.gitignore
This is an exhaustive list of permitted files, if you feel that something is missing then don't hesitate to ask.
# Reverse policy .gitignore
*
!README.md
!LICENSE
!package.json
!index.js
!test.js
!.editorconfig
README.md
# MODULE_NAME
> MODULE_DESC
## Use
BBQbash
$ npm install MODULE_NAME
BBQ
BBQjs
const mod = require('MODULE_NAME')
mod.doMagic() // => Result
BBQ
## Donations
DONATION_TEXT
## Changelog
### 0.1.0 first release
## Contributing
By making a pull request, you agree to release your modifications under the license stated in the next section.
Only changesets by human contributors will be accepted.
## License
LICENSE_SPDX AUTHOR YEAR
LICENSE
TODO: Multiple choice prompt
Only AGPL available right now cause that's the one I use. Open an issue if you need something else. :thumbsup:
LICENSE_TEXT
package.json
TODO:
test
and debug
optional via git.config{
"name": "MODULE_NAME",
"version": "0.1.0",
"description": "MODULE_DESC",
"main": "index.js",
"scripts": {
"lint": "standard",
"test": "tape test.js",
"debug": "node inspect $(npm bin)/tape test.js",
"prepublishOnly": "standard && npm test"
},
"repository": {
"type": "git",
"url": "git://REPO_PREFIX/MODULE_NAME"
},
"author": "AUTHOR",
"license": "LICENSE_SPDX",
"bugs": {
"url": "REPO_PREFIX/MODULE_NAME"
},
"homepage": "REPO_PREFIX/MODULE_NAME"
}
index.js
// SPDX-License-Identifier: LICENSE_SPDX
test.js
const test = require('tape')
test('desc', t => {
t.end()
})
.editorconfig
root = true
[*]
indent_style = space
indent_size = 2
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
A Git repository is an interdimensional holy ground, period.
It is a shared resource between you and countless other individuals present and future - each with their own configurations, workflows, tooling, integrations and platforms.
It is pointless to assume which decorations will be popular tomorrow or guess which services will still exist in 10 years - the more you add the more you commit to maintain; like a loop without a break.
I believe that the code is the most significant component of any repository and the only component worth my time. I also strongly suggest that it should be written in the same form that it is exported to stop messing up introspection for other people.
If you find yourself wanting for more, then maybe it's time for you to split your code into a separate module - or simply purity might not be for you.
By making a pull request, you agree to release your modifications under the license stated in the next section.
Only changesets by human contributors will be accepted.
FAQs
Template to generate low maintenence JS modules
The npm package create-pure receives a total of 0 weekly downloads. As such, create-pure popularity was classified as not popular.
We found that create-pure demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.